Dear All,
the following MWE works fine, but when that 'First line' is uncommented, I
am getting 'Undefined control sequence' error in the console (ConTeXt -
2014.06.22).
\starttext
\startcolumns[n=2]
%First Line
\testcolumn[2]\input{tufte}
\stopcolumns
\stoptext
Any idea what is wrong here
On 12/3/2013 4:40 PM, Hans Hagen wrote:
On 12/3/2013 3:10 PM, Lars Huttar wrote:
...
Thanks again for your work on this.
We're continually reevaluating whether we can use the beta or need to
stick with the stable version. At the moment, it looks like we'll be
sticking with the stable
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
\setuptolerance[verytolerant]
\starttext
\startmixedcolumns
\dorecurse{4}{\input ward \par}
\testcolumn[10
}{\input ward \par}
\testcolumn[10][-1pt] % 10 lines - 1pt slack
\dorecurse{2}{\input ward \par}
\stopmixedcolumns
\stoptext
Ok. It looks like the second parameter to \testcolumn is now required
(it didn't used to be).
i'll fix that
What does this slack value do? Does it mean
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated 2013-11-28 19:45. Is that beta? I may
wait for the next one
On 11/29/2013 12:26 PM, Lars Huttar (SIL gmail) wrote:
On 11/28/2013 1:34 PM, Hans Hagen wrote:
That macro was never meant for mixed columns. I made a variant that
works ok in mixed columns which will be in the next beta.
Excellent. I will give it a try.
I see a context-setup-win64 dated
we couldn't get column balancing
to work in columnsets).
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection
in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so
when we
were about to start a new subsection heading, we could prevent it
being
an orphan at the bottom of the column; and when starting a paragraph
with a hangaround graphic
On 11/22/2013 11:37 PM, Lars Huttar wrote:
On 11/22/2013 4:59 PM, Hans Hagen wrote:
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were
On 11/22/2013 4:59 PM, Hans Hagen wrote:
On 11/20/2013 11:12 PM, Lars Huttar wrote:
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do
in columnsets).
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection heading, we could prevent it being
an orphan
On 11/20/2013 4:47 PM, Lars Huttar wrote:
However one thing we do miss from columnsets is the control over widows
orphans in two ways: \testcolumn, and \setupcolumnsetlines.
\testcolumn[n] allowed us to do a conditional column break, so when we
were about to start a new subsection heading, we
13 matches
Mail list logo
